| Portal
Profile Admin. |
Knowledge portal interacts with
portal profile administration. |
Knowledge user needs to adjust
the portal profile, security information, or configuration information. |
The knowledge user will be able
to set knowledge portal profile types and, where appropriate knowledge portal view. The
knowledge portal profile administration component may be used to regulate security and
other system configuration requirements. |
| Knowledge
Community Member Management |
Knowledge portal interacts with
knowledge community member management; Community member information may be used by other
knowledge components, for example, artifact classification, or project resources. |
A knowledge community member
needs to be added changed or deleted; Another knowledge component requires community
membership information. |
Knowledge community membership
information will be registered, maintained, and made available to other knowledge
components. Security and access privileges may be set in this component. Knowledge
community members may be deleted. |
| Project/Focus
Area Definition And Tracking |
Knowledge portal interacts with
Project/Focus Area Definition And Tracking. An interface to project management software. |
Process workflow definition needs
to be added, revised, or deleted; Project definition needs to be added, revised or
deleted; A project needs to be tracked. |
Business process workflow
information will be maintained both as workflow diagrams and is textual information;
Projects or knowledge community focus areas will be set up, maintained and tracked. |
| Knowledge
Collaboration |
The knowledge portal interacts
with the knowledge collaboration knowledge component. The knowledge collaboration
knowledge components establish interfaces between various knowledge community members. |
Knowledge users require a virtual
meeting; Knowledge users require Virtual Meeting Facilitation Tools; knowledge users wish
to interface with email; knowledge users require instant messaging, that is an instant
knowledge exchange between two knowledge community members; Knowledge users wish to engage
in threaded discussions; Knowledge users wish to set up a chat session. |
Virtual meetings allow knowledge
community members to meet in an effective way, regardless of their physical location. In
some cases virtual meetings maybe facilitated using facilitation support tools. The
knowledge collaboration component should be integrated into the electronic mail system so
that email may be an integral part of the knowledge management system. Knowledge exchange
forums take the form of threaded discussions. When knowledge exchange contains very
valuable information the knowledge collaboration component needs a facility to turn a
discussion into a knowledge artifact and to classify it, store it and make it available to
search engines. Knowledge exchange forums may also take the form of online chats. Like
threaded discussions, the results of the chat may become a knowledge artifact. |
| Knowledge
Community Lessons Learned. |
The Knowledge Portal interacts
with the Knowledge Community Lessons Learned Knowledge Component. The Lessons Learned
Knowledge Component also interacts with the Knowledge Asset/Artifact Management Knowledge
Component. |
Periodically, knowledge community
members may wish to record tips, tricks, or other lessons learned for the benefit of other
knowledge community members. At the end of a project, an after-action report should record
any lessons learned during the project |
Lessons learned, in the form of
tips, tricks, or after action reports, will be recorded, maintain, and archived. The
lessons learned should be stored in the knowledge repository as a knowledge artifact and
he managed by the knowledge artifact management knowledge component. |
| Knowledge
Asset/ Artifact Management |
The knowledge portal interacts
with the knowledge asset/artifact management knowledge component. The knowledge
collaboration and lessons learned knowledge components interface and interact with the
knowledge asset/artifact management knowledge component. The search engine component also
needs to interact with the knowledge artifacts stored within the knowledge repository. |
Knowledge users need to capture
knowledge artifacts, transform them into a usable form, classify them, and make them
available globally in the knowledge repository. |
The Knowledge Asset/Artifact
Management Knowledge Component will facilitate knowledge artifact entry by means of
keyboard, voice recognition, document scanning, and file up loads. Knowledge artifact
entry will be supported by a document workflow system. Knowledge artifacts are classified
in many ways in order that the artifact may be found by a search engine utilizing one or
more of the artifact classifications in its search. An artifact may be classified
according to who uses it or by who are impacted by it. Certain attributes of the artifact
may be used as classifiers and later as search criteria. Key dates and location
information may be used as classifiers also. The purpose of the artifact will be recorded
as an attribute of the artifact and used as a classifier. Artifact information may be
stored in an artifact index database. The artifacts themselves may be stored in the
knowledge repository. Artifacts are entered, classified and stored so that they may be
accessed and distributed to knowledge users with a need to know. The knowledge
asset/artifact management component requires a number of facilities to support access and
distribution. Artifact management will contain a search mechanism which uses classifiers
to focus on artifacts needed, a security mechanism, a check-in, check-out mechanism, data
and knowledge mining facilities, and the ability to make artifacts available to Internet
and Intranet search engines. |
| Knowledge
Community Description |
The Knowledge Portal interacts
with the Knowledge Community Description Knowledge Component. |
Knowledge users will wish to
describe their knowledge community in terms of who they are, what they do, when and where
they do it, how they do it, and why they do it. |
A knowledge community must be
able to do describe itself in terms of who are its members, who were impacted by the
community, who the community partners with, what the community does, when things get done
by the community, how things are done by the community, and why the community exists the
first place. |
| Enterprise
Architecture |
The Knowledge Portal will
interface with the Enterprise Architecture Knowledge Component. Enterprise Architecture
models may be stored as knowledge artifacts and accessed by means of the Knowledge
Asset/Artifact Management knowledge component. |
Knowledge users may wish to
generate and maintain enterprise architecture information, business, application, and
technology architecture models, the including the supporting meta data. |
Enterprise architecture models
and meta data may be generated by means of Web-enabled CASE tools, or by means of Web
publication mechanisms from the CASE tools themselves. By making enterprise architecture
models and meta data available to the Knowledge Artifact Management Knowledge Component,
they will be able to be found using Internet search engines. |
| Search
Engines |
The knowledge portal will
interface with the Search Engines Knowledge Component. The Search Engines will interface
with the knowledge asset/artifact management knowledge component. |
Knowledge users may wish to
search their own knowledge community WebSite. They may wish to perform searches across the
whole enterprise intranet, or across the whole Internet. |
The Search Engine Knowledge
Component will support searches limited to individual projects or sites, full Intranet
searches, and searches across the whole Internet. The searches may be index searches or
may be full artifact content searches. |